Skip to content

test(scrolling): correctly treat TestBed.compileComponents as async #14922

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 25, 2019

Conversation

jelbourn
Copy link
Member

Tests for cdk/scrolling previously assumed that Test.compileComponents
completes synchronously, immediately instantiating components after
calling the compile. This is not true, and the tests only work by
coicidence. With ivy, this is not as lenient and starts failing.

@jelbourn jelbourn added pr: merge safe target: patch This PR is targeted for the next patch release labels Jan 23, 2019
@jelbourn jelbourn requested review from crisbeto and mmalerba January 23, 2019 01:01
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 23, 2019
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Tests for cdk/scrolling previously assumed that Test.compileComponents
completes synchronously, immediately instantiating components after
calling the compile. This is not true, and the tests only work by
coicidence. With ivy, this is not as lenient and starts failing.
@jelbourn jelbourn force-pushed the scroll-sync-compile branch from 5e1e728 to 687a5ea Compare January 23, 2019 21:30
@jelbourn
Copy link
Member Author

Added the missing async

@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 23, 2019
@andrewseguin andrewseguin merged commit 05927b3 into angular:master Jan 25, 2019
andrewseguin pushed a commit that referenced this pull request Jan 25, 2019
…14922)

Tests for cdk/scrolling previously assumed that Test.compileComponents
completes synchronously, immediately instantiating components after
calling the compile. This is not true, and the tests only work by
coicidence. With ivy, this is not as lenient and starts failing.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants